Skip to main content
A Collection is only as useful as the curation behind it. The patterns below come from how partners ship Collections to district networks and how educators bundle resources for colleagues.

​
Pick a clear purpose

Every Collection should answer one question for the recipient: what is this for? The strongest Collections have a tight, specific scope:
  • “Onboarding apps for new Algebra 1 teachers”
  • “Writing tools aligned to ELA grade 6 standards”
  • “Classroom tools for the spring AI literacy unit”
Avoid catch-all Collections. A bundle named “Useful apps” tells recipients nothing about when to use it. A bundle named “Apps for the first week of school” gives them a job to do.

​
Aim for 5 to 12 apps

The sweet spot for most Collections is 5 to 12 apps. Smaller bundles can feel thin; larger ones overwhelm. If you have more than 15, ask whether you really have one Collection or several. A few exceptions:
  • Onboarding bundles can be smaller (3 to 5 apps) to keep the entry point simple
  • Curriculum bundles can be larger if structured around units or weeks

​
Write a description that orients the recipient

The Collection description is your chance to set context. Aim for two to four sentences that cover:
  1. Who it’s for: the audience or role
  2. What’s inside: the kind of apps and the goal
  3. When to use it: situation, unit, or pacing if relevant
Example:
Apps for the first three weeks of the spring AI literacy unit. Includes tools for prompt engineering practice, source evaluation, and a reflection journal. Suitable for grades 8 to 12.

​
Order matters

Drag the apps in your Collection into a sensible sequence. Recipients scan top to bottom. Put the entry-point app first. Group related apps together. Save edge cases or supplementary tools for the end.

​
Test before sharing

Before sharing a Collection externally, do two checks: Open it as a recipient would. Switch to a workspace where you have member-level access and add the Collection. Confirm the apps work, the order makes sense, and the descriptions read clearly. Read the descriptions cold. If you cannot tell what an app does from its description alone, rewrite it before shipping the Collection.

​
Plan for updates

Collections live longer than apps. When you ship a Collection to partner districts, you are committing to maintain it. Set a cadence:
  • Quarterly review. Check that every app still loads, still aligns to the goal, and still reflects current pedagogy
  • Annual refresh. Cut apps that no recipients use, add apps that fill gaps reported by recipients
  • Versioned communication. When you make significant changes, send a note to recipients so the change isn’t a surprise

​
Examples by use case

Starter packs. “Welcome to Playlab” Collections with 4 to 6 apps that get a new teacher productive in their first week. Curriculum sets. Bundles aligned to a unit, course, or grade-level scope and sequence. Often 8 to 15 apps with a clear order. Department resources. Subject-specific apps for one department across schools. Useful for district admins shipping to math, ELA, or special education teachers. Pilot bundles. Apps for a research pilot, intervention, or new program. Smaller and tightly scoped, often paired with a feedback loop. Conference companions. Apps to run alongside a workshop, training, or PD session. Time-bound, with clear instructions in each description.

​
Key points

  • Aim for 5 to 12 apps with one clear purpose
  • Write a description that names the audience and the use case
  • Test the Collection as a recipient would before sharing externally

​
FAQ

You can. Apps shared with you can be added to your Collections if your access permits. Recipients still get access through your Collection. The original owner is unchanged.
Make multiple Collections. There is no per-recipient customization on a single Collection. Multiple targeted Collections beats one sprawling bundle.
Unshare it from each recipient, then delete it from your org. Recipients lose access on unshare; activity history is preserved.
Yes. The Collection’s activity view shows aggregate usage per app per recipient org. Use that data to identify which apps are working and which can be cut.
Yes. Recipients trust your name on the bundle. An unfinished or low-quality app reflects on the Collection and on you.
Last updated: 06-01-2026 Contact us at [email protected]